Method and system for providing location-based services in multiple coverage area environments

ABSTRACT

A resource request that is originated by a short-range wireless communications device originates a request. A location indicator is added to the resource request that identifies a location of the WCD. The location indicator is based on a coverage area within an access point that forwarded the resource request. Then, the resource request is forwarded to a content server.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is related to U.S. application Ser. No. 10/291,567,filed on even date herewith, entitled “Method and System for ProvidingLocation-Based Services,” which is incorporated herein by reference inits entirety.

FIELD OF THE INVENTION

The present invention relates to communications. More particularly, thepresent invention relates to techniques for providing customized contentto wireless communications devices across a communications network.

BACKGROUND OF THE INVENTION

Communications systems currently provide end-users with the capabilityto receive content items made available by content servers andproviders. For example, end-users can receive multimedia broadcasts,audio broadcasts, images, data files, electronic documents, and databaseentries from various content servers. Such content items are deliveredacross a wireless network to portable end-user devices. Examples ofportable end-user devices include wireless telephones, wireless personaldigital assistants (PDAs), and portable computers having wirelesscommunications capabilities.

Bluetooth is a system that enables wireless communications devices torequest and receive resources from servers. Bluetooth defines ashort-range radio network, originally intended as a cable replacement.It can be used to create ad hoc networks of up to eight devices, whereone device is referred to as a master device. The other devices arereferred to as slave devices. The slave devices can communicate with themaster device and with each other via the master device. The BluetoothSpecial Interest Group, Specification Of The Bluetooth System, Volumes 1and 2, Core and Profiles: Version 1.1, Feb. 22, 2001, describes theprinciples of Bluetooth device operation and communication protocols.This document is incorporated herein by reference in its entirety. Thedevices operate in the 2.4 GHz radio band reserved for general use byIndustrial, Scientific, and Medical (ISM) applications. Bluetoothdevices are designed to find other Bluetooth devices within theircommunications range and to discover what services they offer.

Other short-range networks also exist. For example, wireless local areanetworks (WLANs), such as IEEE 802.11 and HIPERLAN also enable wirelesscommunications devices to request and receive resources from servers.

In wireless environments, the location of a portable communicationsdevice may affect the type of information desired when its user makes ageneric request for information. For instance, when requestingdirections to a particular destination, a user would prefer thedirections to be based on the user's current location.

To provide for such location-based content, a server or content providerthat receives a request for content must learn the location of therequesting device. Accordingly, there is a need to provide devicelocation information along with requests.

SUMMARY OF THE INVENTION

The present invention provides techniques for adding information, suchas location indicators, to resource requests that are originated bywireless communications devices (WCDs). Accordingly, a method and systemof the present invention obtains location-based information services.This method and system receives a WCD-originated resource request. Themethod and system add a location indicator to the resource request thatidentifies a location of the WCD. This location indicator is based on acoverage area of an access point that is in wireless communication withthe WCD. Then, the method and system forward the resource request to acontent server. The location indicator associated with the coverage areamay be predefined or dynamically changing.

The location indicator may include location coordinates. Additionally,the location indicator may indicates a vertical position of the WCD. Theresource request may be of different protocols. For example, theresource request may be a hypertext transfer protocol (HTTP) request ora wireless application protocol (WAP) request. In embodiments of thepresent invention, the location indicator may be selectively added tothe resource request when the resource request identifies a suitabledestination domain.

In addition to location indicators, the method and system may add othertypes of information to the request. For instance, the method and systemmay add user profile information and/or WCD class information to theresource request. Also, the method and system may add deviceidentification information to the request, such as, a physical deviceaddress. An example of a device address is a Bluetooth Device Address(BD_ADDR). The content server could use this address to authenticate theoriginating WCD.

Various techniques may be employed to add such information to therequest. For example, additional information may be inserted into aUniform Resource Locator (URL). Alternatively, additional informationmay be inserted into one or more headers of the resource request. Theseheaders may be extension headers.

The method and system may also selectively add information to theresource request, for example, the system and method may add informationwhen the resource request identifies a suitable (or appropriate)destination domain, and/or when the originating WCD is one of apredetermined one or more WCDs.

The present invention is also directed to an apparatus for providinglocation-based services. The apparatus includes a location managerdatabase and a location appending unit. The location manager databasestores location indicators for short-range wireless communicationsdevices (WCDs). The location indicator for each WCD is determined from acoverage area of an access point that supports a wireless connectionwith the WCD. The location appending unit receives resource requestsoriginated by the WCDs, and for each request, adds the locationindicator that corresponds to the requesting WCD.

A further apparatus of the present invention includes two or moreshort-range wireless communications module for communicating with WCDs,and a network interface that is coupled to a data network infrastructurefor enabling communication with at least one content server. Eachshort-range wireless communications module provides a coverage area tosupport communications with WCDs. The apparatus further includes amemory, and a processor. The processor executes instructions stored inthe memory for: (1) receiving a resource request originated by awireless communications device (WCD) through the short-range wirelesscommunications module; (2) adding to the resource request a locationindicator that identifies a location of the WCD; and (3) forwarding theresource request, which includes the added location information to acontent server through the network interface. The location indicator isbased on a coverage area through which the WCD communicates.

A further method and system of the present invention receives a resourcerequest originated by a short-range WCD and forwards the request to acontent server. The method and system also receives from the contentserver an instruction for a location indicator that identifies alocation of the WCD, and determines this location indicator. Thelocation indicator is determined based on a location of an access pointthat is in communication with the WCD. The method and system sends thislocation indicator to the content server.

The present invention is also directed to computer program productsincluding a computer useable medium having recorder computer programlogic. These computer program products enable a processor to provide themethods, systems, and apparatuses of the present invention.

The present invention advantageously provides for device locationinformation to accompany requests for resources. Further features andadvantages will be apparent from the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings, like reference numbers generally indicate identical,functionally similar, and/or structurally similar elements. The drawingin which an element first appears is indicated by the leftmost digit(s)in the reference number. The present invention will be described withreference to the accompanying drawings, wherein:

FIG. 1 is a block diagram of a short-range wireless communicationsenvironment according to an embodiment of the present invention;

FIG. 2 is a block diagram of a database architecture according to anembodiment of the present invention;

FIG. 3 is a block diagram of a host controller implementation accordingto an embodiment of the present invention;

FIGS. 4A and 4B are flowcharts illustrating operational sequencesinvolving a resource requests originated by wireless communicationsdevices according to embodiments of the present invention;

FIG. 5 is a block diagram of a Bluetooth environment according to anembodiment of the present invention;

FIG. 6 is a flowchart illustrating an operational sequence involving aresource request originated by a wireless communications deviceaccording to an embodiment of the present invention;

FIG. 7 is a block diagram of an access point implementation that addsinformation to requests received from wireless communications devices,according to an embodiment of the present invention;

FIG. 8 is an elevation view of a scenario where two access points arelocated on different levels of a shopping mall according to anembodiment of the present invention;

FIG. 9 is a diagram of an exemplary operational environment according toan embodiment of the present invention;

FIG. 10 is a block diagram of a database architecture according to anembodiment of the present invention;

FIG. 11 is a block diagram of a host controller implementation accordingto an embodiment of the present invention;

FIG. 12 is a block diagram of an operational environment according to anembodiment of the present invention;

FIG. 13 is a block diagram of an access point implementation thatprovides multiple coverage areas, according to an embodiment of thepresent invention;

FIGS. 14A and 14B are elevation views involving a multiple coverage areascenario; and

FIG. 15 is a block diagram of an exemplary computer system.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

I. Operational Environment

Before describing the invention in detail, it is helpful to describe anenvironment in which the invention may be used. FIG. 1 is a blockdiagram of a short-range wireless communications environment in whichthe present invention may be employed. This exemplary environmentincludes multiple wireless communications devices (WCDs) 102, aplurality of access points 106, a host controller 110, a gateway 112, adata network 114, and a content server 116.

WCDs 102 engage in end-to-end client-server communications with contentserver 116. Such communications involve WCDs 102 sending requests forresources to content server 116. In response to these requests, contentserver 116 transmits content, such as hypertext documents, to therequesting WCDs 102.

Each WCD 102 may be a wireless mobile phone, a wireless PDA, a pager, atwo-way radio, a smartphone, a personal communicator, or any otherwireless device apparent to persons skilled in the relevant arts. WCDs102 transmit requests according to protocols, such as the wirelessapplication protocol (WAP) and the hypertext transfer protocol (HTTP).

When engaging in WAP communications with content server 116, a WCD 102functions as a WAP client. To provide this functionality, WCD 102includes a processor that executes WAP client software. WAP softwarecontains components, such as a Wireless Markup Language (WML) Browser, aWMLScript engine, a Push Subsystem, and a Wireless Protocol Stack thatare known to persons skilled in the relevant art(s).

WAP-enabled WCD 102 may access small files called decks, which are eachcomposed of smaller pages called cards. Cards are small enough to fitinto a small display area that is referred to as a microbrowser. Thesmall size of the microbrowser and the small file sizes are suitable foraccommodating low-memory devices and low-bandwidth communicationsconstraints imposed by the wireless communications systems, such asBluetooth.

Cards are written in the Wireless Markup Language (WML), which isspecifically devised for small screens and one-hand navigation without akeyboard. WML is scaleable so that it is compatible with a wide range ofdisplays that covers two-line text displays, as well as large LCDscreens found on devices, such as smart phones, PDAs, and personalcommunicators. WML cards may include programs written in WMLScript,which is similar to JavaScript. However, through the elimination ofseveral unnecessary functions found in these other scripting languages,WMLScript makes minimal processing and memory demands WCDs 102.

Requests travel from a WCD 102 to content server 116 through an accesspoint 106, host controller 110, gateway 112, and data network 114.Responses to these requests travel from content server 116 throughgateway 112, and access points 106. From each received request, contentserver 116 may select content that is appropriate for the requesting WCD102. This selection may be based on the location and/or othercharacteristics of the requesting WCD 102.

In the environment of FIG. 1, WCDs 102 communicate with access points106 according to a short-range wireless communications standard, such asBluetooth. These communications may employ a profile, such as theBluetooth Personal Area Network (PAN) profile.

Each access point 106 has a predetermined location and a coverage area104. Each access point 106 may communicate with devices (such as WCDs102) that are within its respective coverage area 104. Coverage areas104 may vary in shape and size. However, for short-range communicationssystems, coverage areas are generally small. For instance, coverageareas for Bluetooth access points are typically between 10 and 30 metersin radius.

FIG. 1 shows that each access point 106 is connected to host controller110 by links 108 a-e. These links may be either wireless or wired links.For example, links 108 may be short-range (e.g., Bluetooth) links.Although FIG. 1 shows host controller 110 as a distinct entity, it mayalternatively be located within one of access points 106.

When host controller 10 is implemented as a distinct entity, it may beplaced in a variety of locations. For instance, host controller 110 maybe located within one or more of coverage areas 104. For such locations,host controller 110 may exchange information with access points 106through short-range wireless links.

Host controller 110 receives requests from access points 106 that areoriginated by WCDs 102. Host controller 110 may then add information tothese requests. Host controller 110 forwards these requests to gateway112

As shown in FIG. 1, host controller 110 is connected to a gateway 112.Gateway 112 provides connectivity to data network 114. To provide thisconnectivity, gateway 110 may perform functions, such as protocolconversion and buffering.

Data network 114 provides accessibility to information resources, suchas content server 116. In embodiments of the present invention, datanetwork 114 is a packet network, such as the Internet, where datapackets are exchanged according to various protocols, such as TCP/IP,HTTP, and WAP.

While not shown in FIG. 1, one or more of the access points 106 may bedirectly connected to gateway 112 by either wired or wireless links toallow direct access to data network 114. Also, one or more of the accesspoints 106 may be directly connected to data network 114 to provide evenmore direct access to information resources, such as content server 116.Such communications allow content to be delivered to WCDs 102 withoutpassing through host controller 110, and possibly even gateway 112.

WCDs 102 are portable devices. Therefore, during operation, they maymove between coverage areas 104 and communicate with different accesspoints 106. Thus, at any moment in time, the location of a particularWCD 102 is indicated by the location of the access point 106 that it iscommunicating with. This location indication is quite accurate becausein short-range wireless environments, each coverage area 104 isrelatively small.

In fact, this location indication may identify vertical positions ofWCDs 102 in certain environments. For instance, in structures such asmulti-level buildings, RF signals transmitted by Bluetooth access pointsare typically not strong enough to penetrate through flooring material,such as concrete. Therefore, with systems such as Bluetooth, verticalpositions of WCDs 102 may be determined from the identity of thecorresponding access point 106.

To provide content server 116 with WCD 102 locations, host controller110 processes requests received from WCDs 102. In particular, uponreceiving a request, host controller 110 determines the location of theWCD 102 that originated the request. Then, host controller 110 adds thislocation to the request, and forwards the request along its route tocontent server 116. In the environment of FIG. 1, the next destinationalong this route is gateway 112.

Content server 116 receives the request and, from information added tothe request, such as an accurate location indicator, may advantageouslyprovide a variety of location-based service features that have not beenpreviously available.

II. Database Architecture

Host controller 110 determines WCD 102 locations from the location ofcorresponding access points 106. In order for host controller 110 tokeep track of WCD 102 locations, embodiments of the present inventionemploy a database architecture that is shown in FIG. 2. In thisarchitecture, databases are included within host controller 110 andaccess points 106 a-e.

As shown in FIG. 2, each access point 106 includes a connection database202. Connection databases 202 each provide a listing of the WCD 102connections supported by the corresponding access point 106. Forinstance, connection database 202 b in FIG. 2 shows that access point106 b supports connections with WCDs 102 a and 102 c. Connectiondatabase 202 d shows that access point 106 d supports a connection withWCD 102 b. Connection database 202 e shows that access point 106 esupports a connection with WCD 102 d.

FIG. 2 shows that host controller 110 includes a location managerdatabase 210. Location manager database 210 includes an access pointconnection portion 220, an access point location portion 222, and alocation manager portion 224.

Access point connection portion 220 stores connection information foreach access point 106. Thus, access point connection portion 220 storescopies of information contained in each of connection databases 202. Tokeep these copies updated, access points 106 transfer the contents oftheir respective databases 202 to host controller 110 eithercontinually, or at predetermined time intervals.

Access point location portion 222 stores location information for eachof access points 106. This location information (also referred to as“location handles”) may be in the form of coordinates. Such coordinatesmay be rectangular (i.e., x, y, z). Alternatively, such coordinates maybe latitude, longitude, and altitude. In further alternatives, othersuitable coordinate systems may be employed.

Location manager portion 224 stores location indicators for the WCDs 102that are communicating with access points 106. Accordingly, locationmanager portion 224 includes records that each include a WCD 102identifier, such as a BD_ADDR, and a corresponding location indicator.Since each access point 106 has a predetermined location, its connectedWCDs 102 have approximately the same location (e.g., within 10-30 metersin Bluetooth implementations). Using the location handles in accesspoint location portion 222, a location indicator is assigned to each WCD102 that is communicating with an access point 106. As shown in FIG. 2,location manager portion 224 stores a location indicator for each ofWCDs 102 a-d.

III. Host Controller

The database implementation of FIG. 2 is utilized by processing elementswithin host controller 110. FIG. 3 is a block diagram of a hostcontroller 110 implementation that shows these processing elements. Asshown in FIG. 3, host controller 110 includes a location appending unit302, a database management unit 304, and a communications interface 305.FIG. 3 also shows that in addition to location manager database 210,host controller 110 includes a domain database 306. These elements maybe implemented with hardware, software, firmware, or any combinationthereof.

Location appending unit 302 appends location indicators toWCD-originated requests that are received from access points 106. For aparticular request, this appending includes identifying the originatingWCD 102, and retrieving from location manager portion 224 the locationindicator that corresponds to this WCD 102. After this retrieval, WCD102 appends the location indicator to the request, and forwards therequest to gateway 112. This feature allows content server 116 toprovide accurate location-based services.

Location appending unit 302 may also add other WCD 102 and/or userrelated information to received requests. Such features may be employedin circumstances, such as when a user has authorized the operator ofhost controller 110 to add such information to requests. This featureenables user profile based and/or device class based service creation inaddition to location-based services.

Database management unit 304 performs functions related to themaintenance of databases within host controller 110. In particular,database management unit 304 receives connection database 202 recordsfrom access points 106 and upon receipt of these records, updates thecontents of portion 220 in location manager database 210. In addition,database management unit 304 maintains location manager portion 224.This involves establishing and updating records in location managerportion 224. As described above, these records each include a WCD 102identifier, such as a BD_ADDR, and a corresponding location indicator.

As shown in FIG. 3, communications interface 305 is coupled to locationappending unit 302 and database management unit 304. Communicationsinterface 305 exchanges information with other entities that areexternal to host controller 110. For example, communications interface305 receives from access points 106 content requests and informationstored in connection databases 202. In addition, communicationsinterface 305 transmits requests to their next destination(s) alongtheir route to content server 116. In the environment of FIG. 1, thenext destination is gateway 112.

Such communications may be according to various protocols. For example,communications interface 305 may employ short-range wireless (e.g.,Bluetooth) communications techniques to communicate with access points106 and/or gateway 112. Alternatively, communications interface 305 mayemploy wired communications techniques or a combination of wireless andwired techniques in performing such communications.

Communications interface 305 also exchanges information with elementswithin host controller 110. For instance, communications interface 305receives WCD-originated content requests from access points 106 andforwards these requests to location appending unit 302 for processing.Once processed, communications interface 305 receives these requestsfrom location appending unit 302, and forwards these requests alongtheir route to content server 116. These steps may involve extractingcontent requests from transmission units, such as communications packetsreceived by access points 106, and reformatting requests received fromlocation appending unit 302 for transmission.

IV. Filtering

Host controller 110 may selectively append location indicators torequests. Thus, location appending unit 302 may perform “filtering”operations in order to provide appended information only to certainrequests.

For instance, location appending unit 302 may append locationinformation to content requests that relate to the location of therequesting WCDs 102. An example of such location-based filtering may beapplied in a shopping mall context, where access points 106 aredistributed at different locations in the mall. When host controller 110receives requests from these access points that are directed toshopping-related content, location appending unit 302 appends locationinformation to the requests. However, when host controller 110 receivesrequests from these access points that are unrelated to shoppingcontent, it does not append any location information to the requests.

Location appending unit 302 may base such determinations on resourceaddress information contained in domain database 306. Thus, uponreceiving a request, location appending unit 302 determines the accesspoint 106 that forwarded the request. Then, location appending unit 302accesses records in domain database 306 that correspond to this accesspoint. These records may include resource identifiers, such as domainnames, that are appropriate for the appending of location information.

The employment of domain database 306 advantageously allows theappending of location information to be a subscription or fee servicepaid by content providers. Namely, the party controlling host controller110 may provide additional information, such as location indicators,only to content servers that subscribe and/or pay for such information.

Host controller 110 may also perform “filtering” operations based on theidentity of the requesting WCD 102. For instance, location appendingunit 302 may selectively append location information only to requestsgenerated by certain WCDs 102. A list of these WCDs 102 may bemaintained in domain database 306. This feature advantageously enablesWCD 102 users to be treated with different levels of service. Forexample, some WCD 102 users may receive premium location-based services,while other may not. Users may be differentiated according to variousschemes. In one such scheme, users that make frequent requests receivelocation-based services.

Filtering operations based on the identity of the requesting WCD 102 maybe performed alone or in combination with other filtering operations,such as the filtering techniques described above.

V. Operation

FIGS. 4A and 4B are flowcharts illustrating operational sequencesaccording to the present invention. These sequences are described withreference to the operational environment of FIG. 1. However, they may beemployed with other environments and network topologies. Also, while theflowcharts show steps being performed in a certain order, other ordersare within the scope of the present invention.

The operational sequence shown in FIG. 4A begins with a step 402. Inthis step, host controller 110 receives a request for content such as aWML document, an HTML document, or other forms of content. Accordingly,the received request includes a resource identifier, such as a uniformresource locator (URL).

Next, in a step 404, host controller 110 determines properties of thereceived request. Examples of such properties include the identity(i.e., the device address) of the requesting WCD 102, and the identityof the forwarding access point 106.

In embodiments of the present invention, the request may not physicallyidentify the requesting WCD 102. Rather, the request may merely containan originating address, such as an IP address. A physical deviceaddress, such as a media access control (MAC) address, may be needed todetermine the corresponding access point 106. In Bluetoothimplementations, such an address is a Bluetooth device address (BD_ADR).Accordingly, step 404 may comprise accessing a server, such as a dynamichost configuration protocol (DHCP) server to determine the deviceaddress of the requesting WCD 102. Alternatively, step 404 may comprisesending (e.g., broadcasting) a message, such as an address resolutionprotocol (ARP) message to access points 106 and/or WCDs 102 to receivethis physical address. Such techniques are described below withreference to FIG. 6.

Once the device address is determined, host controller 110 may determinethe corresponding access point 106. As described above with reference toFIG. 2, the corresponding access point 106 may be determined from, forexample, location manager database 210.

In a step 406, host controller 110 determines whether it is appropriateto add additional information to the request. If so, then a step 408 isperformed. Otherwise, operation proceeds to a step 410. With referenceto FIG. 3, step 406 may comprise accessing domain database 306 accordingto the resource identified in the request and the forwarding accesspoint 106 to determine whether adding information to the request isappropriate. Also, step 406 may comprise accessing domain database 306to determine whether adding information to requests from the requestingWCD 102 is permitted.

In step 408, host controller 110 adds additional information to therequest. This step may additionally or alternatively comprise locationappending unit 302 appending a location indicator to the request. Thisstep may comprise host controller 110 (e.g., location appending unit302) adding other information to the request that conveyscharacteristics of the requesting WCD 102. Examples of such additionalinformation include user profile information, the device class of therequesting WCD 102 (e.g., wireless phone, PDA, etc.), and the physicaladdress of the requesting WCD 102.

In step 410, host controller 110 forwards the request along its route tocontent server 116. In the topology of FIG. 1, the next point along thisroute is gateway 112.

Next, in a step 412, content server 116 receives the request. After step412, a step 414 is performed. In step 414, content server 116 extractsthe indicated resource from the request and any additional informationcontained in the request, such as an added location indicator.

A step 416 follows step 414. In this step, content server 116 selectscontent that is based on the resource identifier and additionalinformation (such as a location indicator) contained in the request.Next, in a step 418, content server 116 transmits the selected contentto the requesting WCD 102.

The operational sequence shown in FIG. 4B is similar to the sequenceshown in FIG. 4A. However, unlike the sequence in FIG. 4A, hostcontroller 110 does not add information to received requests until itreceives an instruction from content server 116.

This sequence begins with a step 450. In this step, host controller 110receives a request for content such as a WML document, an HTML document,or other forms of content. Accordingly, the received request includes aresource identifier, such as a uniform resource locator (URL).

In step 454, host controller 110 forwards the request along its route tocontent server 116. In the topology of FIG. 1, the next point along thisroute is gateway 112. Next, in a step 456, content server 116 receivesthe request.

In a step 458, content server 116 determines whether it would prefer toreceive additional information, such as a location indicator. If so,then operation proceeds to a step 460. Otherwise operation proceeds to astep 468.

In a step 460, content server 116 sends an instruction to hostcontroller 110, which may arrive at host controller 110 via gateway 112.This instruction directs host controller 110 to provide additionalinformation regarding the WCD 102 that originated the request. Suchadditional information may include user profile information, the deviceclass of the requesting WCD 102, and/or the physical address of therequesting WCD 102. This instruction contains information to identifythe requesting WCD 102. For example, in IP networking contexts, suchidentifying information may include the IP address used by therequesting WCD 102.

In a step 462, host controller 110 receives the instruction from contentserver 116. Based on this instruction, host controller 110 accessesinformation corresponding to the WCD 102 that originated the request.For example, based on an address contained in the instruction fromcontent server 116, host controller 110 may obtain a location indicatorfrom location manager database 210.

In response to the request received from content server 116, a step 464follows step 462. In this step, host controller 110 transmits to contentserver 116 the additional information accessed in step 462. In theenvironment of FIG. 1, this additional information may travel throughgateway 112 and across data network 114 to arrive at content server 116.Content server 116 receives this additional information in a step 466.

As shown in FIG. 4B, step 468 follows either step 458 or step 466. Inthis step, content server 116 selects content (i.e., resources). Whenstep 468 follows step 458, this selection is based on the resourceidentifier in the WCD-originated request. However, when step 468 followsstep 466, this selection is based on both the resource identifier in theWCD-originated request and additional information (such as a locationindicator) forwarded by host controller 110 in step 464.

A step 470 follows step 468. In this step, content server 116 transmitsthe selected content to the requesting WCD 102.

In FIGS. 4A and 4B, host controller 110 provides additional informationto content server 116. For instance, FIG. 4A illustrates host controller110 adding information to requests that it receives from WCDs 102.Likewise, FIG. 4B illustrates host controller 110, when instructed,providing WCD-related information to content server 116. However, suchoperations may be performed by other entities. For example, steps402-410, 450, 454, 462, and 464 may be performed by a gateway, such asgateway 112, or a gateway as shown in FIG. 5.

FIG. 5 is a block diagram of a Bluetooth environment where a gateway112′ adds information to requests. The environment of FIG. 5 is similarto the environment of FIG. 1. However, to add this information, gateway112′ relies on information provided by servers that are accessiblethrough data network 114. As shown in FIG. 5, these servers include adynamic host configuration protocol (DHCP) server 502, and a connectionmanager server 504.

In FIG. 5, each WCD 102 may establish a Bluetooth connection with anaccess point 106 according to a personal area networking (PAN) profile.Once establishing a Bluetooth connection with an access point 106, a WCD102 obtains an IP address from DHCP server 502. DHCP server 502 storesthe short-range wireless media access control (MAC) address of each WCD102 that is communicating with an access point 106. In Bluetoothimplementations, this MAC address is in the form of a Bluetooth deviceaddress (BD_ADDR). For each of these MAC addresses, DHCP server 502stores the corresponding IP address. These addresses may be stored in afile, such as a leases file. This storage makes it possible tocross-reference IP addresses and short-range wireless MAC addresses.

As in FIG. 1, each access point 106 in FIG. 5 has a predeterminedlocation. In some implementations, each access point 106 “knows” itspredetermined location. During an initialization procedure, each accesspoint 106 forwards this location to a centralized database (e.g.,location manager database 210). In the environment of FIG. 5, locationmanagement database 210 is stored in connection manager server 504.Thus, connection manager server 504 also stores correspondences betweenWCDs 102 and the access points 106 that support their wirelesscommunications. Access points 106 may transmit these correspondences toconnection manager server 504 at, for example, predetermined timeintervals or whenever these correspondences change.

FIG. 6 shows a sequence of operation for the environment shown in FIG.5. This sequence begins with a step 602. In this step, a WCD 102transmits a WAP request that is forwarded by an access point 106 togateway 112′.

In a step 604, gateway 112′ sends a device ID and location request toconnection manager server 504. This request includes the IP address usedby the requesting WCD 102.

Connection manager server 504 receives this request, and in a step 606,reads the WCD 102 device ID (i.e., its BD_ADDR) from DHCP server 502.Step 606 may comprise transmitting a request to DHCP server 502 thatcontains the IP address used by the requesting WCD 102, and receiving aresponse from DHCP server 502 that contains its BD_ADDR.

From the device ID received in step 606, connection manager server 504determines the location of the requesting WCD 102. This determination isbased on the location of the access point 106 that forwarded the requestto gateway 112′. As described above, connection manager server 504stores correspondences between WCDs 102 and access points 106.

Next, in a step 608, connection manager server 504 sends the location ofthe requesting WCD 102 to gateway 112′. In addition, connection managerserver 504 may also send the device ID of the requesting WCD 102 duringthis step. Upon receipt of this information, gateway 112′ may addinformation to the WAP request. Thus, at this point, gateway 112′performs steps 404-408 of FIG. 4A.

In a step 610, gateway 112′ sends a content request to content server116. Upon receiving this request, content server 116 selects contentbased on the resource identified in the request, as well as on anyadditional information (such as a location indicator) contained in therequest. Next, in a step 612, content server 116 delivers content to therequesting WCD 102 via gateway 112′.

As described above with reference to FIG. 6, the MAC addresses (i.e.,BD_ADDR) of WCDs 102 are obtained from DHCP server 502. However, theseMAC addresses may alternatively be determined through mechanisms, suchas the address resolution protocol (ARP). ARP is protocol used toconvert an IP address into a device address, such as a Bluetoothaddress. According to this protocol, a physical address is determined bybroadcasting an ARP request containing an IP address onto a network. Adevice connected to the network that has the IP address then replieswith its device address.

Also, as described above with reference to FIG. 6, WCD 102 locations areobtained from connection manager server 504. However, as an alternativeto this technique, once gateway 112 receives the MAC address of arequesting WCD 102, it may determine the location of the requesting WCD102 through MAC addresses provided directly by access points 106.

VI. Extension Headers

The present invention provides for the addition of information torequests. Various techniques may be employed to add such information.For instance, additional information may be added to HTTP and WAPrequests as HTML extension headers.

As described herein, users of wireless devices, such as WCDs 102, mayoriginate and send requests for content offered by content providers,such as content server 116. In short-range communications environments,such as the ones shown in FIGS. 1, 5, 9, and 12, such requests passthrough intermediate points. For example, in FIG. 1, such requests maypass through an access point 106, host controller 110, and gateway 112before reaching a content provider. In FIG. 2, requests may pass throughan access point 106 and gateway 112′ before reaching a content provider.

According to the present invention, these intermediate points may addinformation to requests, such as WCD location indicators and/or otherinformation. The employment of extension headers is one technique foradding such information. This technique may be employed in variousprotocols, such as HTTP and WAP. However, for purposes of convenience,the following is a description in the context of HTTP.

Header lines provide information about an HTTP transmission, such as aGET request. Headers may convey various information about originator ofthe HTTP message. For instance, HTTP version 1.0 and 1.1 define a “From”header that specifies an e-mail address of request's originator.

HTTP extensions allow parameters in the form of headers to be added toGET requests that may be visible by the recipient (e.g., content server116) at the HTTP protocol layer. Thus, HTTP extension headers providefor the introduction of new encodings into HTTP messages and theextension of information that may conveyed in a single HTTP message.

A framework for extension headers is described RFC 2774, published bythe Internet Society in 2000. This document is incorporated herein byreference in its entirety. According to the framework of RFC 2774, aparty may specify an extension and assign a globally unique UniformResource Indicator (URI) to the extension.

When a client or server (referred to herein as an agent) employs theextension, it declares its use by referencing the extension's URI in anextension declaration in an HTTP message. This message may containheaders defined by the extension. Based on the extension declaration inthe HTTP message, the recipient of the message deduces how to interpretthe extended message.

Thus, upon receiving WCD-originated requests, an entity that addsinformation (e.g., location indicators) to requests may employ anextension to regenerate or reformat the requests so that they containadditional information. An example of such an extension includes aheader that includes a location code. this location code indicates thelocation of the requesting WCD. As described above, this locationindicator may be based on coordinates of the access point thatcommunicates with the requesting WCD. Thus, the location code mayinclude access point 106 coordinates.

Although extension headers may be employed to add information torequests, other techniques may be applied. For example, common gatewayinterface (CGI) scripts may be employed. Also, information, such as alocation indicator, may be added to a resource indicator, (e.g., aUniform Resource Locator) contained in the request.

VII. Access Point Implementation

In the above examples, host controller 110 and gateway 112′ addinformation to requests. However, in further embodiments of the presentinvention, access points, such as access points 106 may instead addinformation to requests.

FIG. 7 is a block diagram illustrating an access point implementationthat adds information generated by requests received from WCDs 102. Asshown in FIG. 7, this implementation includes a short-range wirelessmodule 702, an access point host 704, a memory 706, a network interface708, and a processor 710.

Access point host 704 is responsible for performing higher protocollayer (e.g., application layer) operations, while short-range wirelessmodule 702 is responsible for lower layer protocol operations. Forexample, in Bluetooth implementations, short-range wireless module 702is a Bluetooth module that performs Bluetooth link manager layer andBluetooth link controller layer functions, as well as the transmissionand reception of RF signals through one or more antennas (not shown).

Access point host 704 and short-range wireless module 702 communicatewith each other according to a host controller interface (HCI) 712.Bluetooth specifies formats for messages and/or packets that cross HCI712. Examples of such standard messages include short-range wirelessmodule 702 requesting a link key from terminal host 704, and accesspoint host 704 providing a link key to short-range wireless module 702.

Network interface 708 provides connectivity to a data networkinfrastructure for enabling communication with at least one contentserver. For instance, in the context of FIGS. 1 and 5, network interface708 provides connectivity to gateways 112 and 112′, respectively.Alternatively, network interface 708 may provide direct connectivity todata network 114.

As shown in FIG. 7, processor 710 overlaps with short-rangecommunications module 702, access point host 704, and network interface708. This overlapping shows that functions performed by these elementsmay be handled by processor 710. Processor 710 and memory 706 may beimplemented as described below with reference to FIG. 15. For example,processor 710 may be a commercially available microprocessor.

Memory 706 stores software components (e.g., instructions) thatprocessor 710 executes to perform various operations. For example,memory 706 stores software components that enable the access point tohandle communications with content server 116 according to protocols,such as WAP and HTTP.

In addition, memory 706 stores software instructions that allow accesspoint host 704 to perform various features of the present invention. Forexample, these instructions provide for host 704 to receiveWCD-originated resource requests through short-range wireless module702. Once such a request is received, these instructions allow host 704to add information to the resource request, such as location indicators.Then, the instructions allow host 704 to forward the resource requestincluding the added location information to a content server, such ascontent server 116. The request is forwarded through network interface708.

These location indicators are based on the location of the access point.An access point may be assigned a location indicator through informationit receives during an initialization process or automatically.Alternatively, an access point may determine its location indicatorthrough services, such as the global positioning system (GPS).

Accordingly the access point implementation of FIG. 7 may performtechniques of the present invention. For example, this implementationmay perform the aformentioned operations of the host controller 110, asdescribed above with reference to FIGS. 4A and 4B.

VIII. Shopping Mall Scenario

FIG. 8 is an elevation view of a scenario where two access points arelocated on different levels of a shopping mall. In particular, FIG. 8shows a first level and a second level that are separated by a floor 801b. An access point 106 f having a coverage area 104 f is placed on thefirst level. Coverage area 104 f encompasses a shoe store 802 and arestaurant 804. Placed on the second level is an access point 106 g thathas a coverage are 104 g. As shown in FIG. 8, coverage area 104 gencompasses a bookstore 806 and a movie theater 808.

Floor 801 b is constructed of a material, such as concrete. Thisprevents coverage areas 104 f and 104 g from overlapping. Therefore,although these coverage areas laterally overlap, they each correspond tovertically distinct locations.

The scenario of FIG. 8 includes two users that are each operating a WCD.More particularly, a user on the first level is operating a WCD 102 e,while a user on the second level is operating a WCD 102 f. In thisscenario, each of these users transmits the same request. However,because of their different locations, these users each receive differentresponses. This location-based content feature is provided through thetechniques described above.

As shown in FIG. 8, each user transmits a request for“shoppingmall.com”. The user on the first level receives a response tothis request that includes a “shoestore-restaurant” resource. This isbecause shoe store 802 and restaurant 804 are within coverage area 104f. In contrast, the user on the second level receives a response thatincludes a “bookstore-movietheater” resource. These resources may eachbe hypertext documents, such as WML or HTML documents.

IX. Multiple Coverage Area Environments

Access points may have multiple coverage areas. These coverage areas maybe distinct, or overlapping. Techniques for providing content providersand servers with WCD-related information in multiple coverage areaenvironments are described with reference to FIGS. 9-14B.

FIG. 9 is a diagram of an exemplary operational environment that issimilar to the environment of FIG. 1. However, the environment of FIG. 9includes access points 906 that each have multiple coverage areas 904.For instance, an access point 906 a has coverage areas 904 a and 904 b.Similarly, an access point 906 b has coverage areas 904 c, 904 d, and904 e. As shown in FIG. 9, WCDs 102 g-j are distributed among thesecoverage areas. In particular, WCD 102 g is within coverage area 904 a,WCD 102 h is within coverage area 904 c, and WCDs 102 i and 102 j arewithin coverage area 904 d.

FIG. 9 shows that each access point 906 is coupled to a host controller910 by a link 908. Links 908 may be either wired or wireless. Hostcontroller 910 is coupled to gateway 112, which provides access to datanetwork 114. As described above, data network 114 provides access tocontent server 116.

In order for host controller 910 to keep track of WCD 102 locations,embodiments of the present invention employ a database architecture thatis shown in FIG. 10. This architecture is similar to the architecture ofFIG. 2 because it includes databases included within host controller 910and access points 906 a-e. However, unlike the architecture of FIG. 2,the architecture of FIG. 10 provides for multiple coverage area accesspoints.

As shown in FIG. 10, each access point 906 includes a connectiondatabase 1002. Each connection database 1002 provides a listing of theWCD 102 connections supported by its access point's coverage areas. Forinstance, connection database 1002 a indicates that access point 906 ahas two coverage areas: 904 a and 904 b. Database 1002 a furtherindicates that access point 906 a supports a connection with WCD 102 gthrough coverage area 904 a. Connection database 1002 b indicates thataccess point 906 b has three coverage areas: 904 c, 904 d, and 904 e. Inaddition, database 1002 b indicates that access point 906 b supports aconnection with WCD 102 h through coverage area 904 c, and connectionswith WCDs 102 i and 102 j through coverage area 904 d.

FIG. 10 shows that host controller 910 includes a location managerdatabase 1010. Location manager database 1010 includes an access pointconnection portion 1020, an access point location portion 1022, and alocation manager portion 1024. Access point connection portion 1020stores connection information for each access point 906. Thus, accesspoint connection portion 1020 stores copies of information contained ineach of connection databases 1002. To keep these copies updated, accesspoints 906 transfer the contents of their respective databases 1002 tohost controller 910 either continually, or at predetermined timeintervals.

Access point location portion 1022 stores location information for eachof the coverage areas provided by access points 906. This locationinformation (also referred to as “location handles”) may be in the formof coordinates. Such coordinates may be rectangular (i.e., x, y, z).Alternatively, such coordinates may be latitude, longitude, andaltitude. In further alternatives, other suitable coordinate systems maybe employed. Each location handle provides a representative location ofa corresponding coverage area 904. this representative location may be acentral location within the corresponding coverage area 904.

Location manager portion 1024 stores location indicators for the WCDs102 that are communicating with access points 906. Accordingly, locationmanager portion 1024 includes records that each include a WCD 102identifier, such as a BD_ADDR, and a corresponding location indicator.For each coverage area, the connected WCDs 102 have approximately thesame location (e.g., within 10-30 meters in Bluetooth implementations).Using the location handles in access point location portion 1022, alocation indicator is assigned to each WCD 102 that is communicatingwith an access point 906. As shown in FIG. 10, location manager portion1024 stores a location indicator for each of WCDs 102.

Host controller 910 may be implemented in a manner similar to theimplementation of FIG. 3. However, instead of database 210, suchimplementations include location manager database 1010. Such animplementation is shown in FIG. 11. FIG. 11 shows that host controller910 further includes a location appending unit 302, a databasemanagement unit 304, a communications interface 305, and a domaindatabase 306. In this implementation, location appending unit 302receives indicators from location manager database 1010 that are basedon coverage area locations instead of just access point locations.

The operational sequences described above with reference to FIGS. 4A and4B may be performed in the environment of FIG. 9. Accordingly, hostcontroller 910 may perform steps 402-410, 450, 454, 462, and 464.However, for this environment, these steps involve providing contentserver 116 with location indicators that are based on coverage arealocations.

Alternatively, such operations may be performed by other entities, suchas a gateway. Accordingly, FIG. 12 is a diagram of an operationalenvironment where a gateway provides additional information to contentserver 116. The environment of FIG. 12 is similar to the environmentshown in FIG. 9. However, in FIG. 12, each access point 906 is coupledto a gateway 1212 that provides WCD-related information to contentserver 116. To provide this information, gateway 1212 relies oninformation received from servers, such as a DHCP server 1202, and aconnection manager server 1204.

The elements of FIG. 12 operate as the elements of FIG. 5. However,unlike connection manager server 504, which contains location managerdatabase 210, connection manager server 1204 contains location managerdatabase 1010. As described above, location manager database 1010maintains correspondences between WCDs and coverage area locations. Eachaccess point 906 provides server 1204 with this information. Thus, inthe environment of FIG. 12, gateway 1212 may provide content server 116with location indicators that are based on the location of coverageareas 904.

In environments, such as the ones shown in FIGS. 9 and 12, coverageareas may be dynamic. That is, a coverage area's physical properties(e.g., shape, size, location, and orientation) may change over time. Incertain scenarios, such changes may correspond to real-world events. Forinstance, in a shopping mall, the location of coverage areas may changeas businesses open and close. Such changes allow coverage areas to beadvantageously placed in locations that are useful to consumers carryingWCDs.

FIG. 13 is a block diagram of an access point implementation thatprovides multiple coverage areas. This implementation includes multipleshort-range wireless modules 1302, each corresponding to a respectivecoverage area. In particular, FIG. 13 shows that a module 1302 acorresponds to a coverage area 904 f, and a module 1302 b corresponds toa coverage area 904 g. The access point implementation of FIG. 13further includes an access point host 1304, a memory 1306, a networkinterface 1308, and a processor 1310.

Access point host 1304 is responsible for performing higher protocollayer (e.g., application layer) communications with modules 1302 a and1302 b. In contrast, short-range wireless modules 1302 are eachresponsible for lower layer protocol operations in communicating withWCDs through its respective coverage area. For example, in Bluetoothimplementations, each short-range wireless module 1302 is a Bluetoothmodule that performs Bluetooth link manager layer and Bluetooth linkcontroller layer functions, as well as the transmission and reception ofRF signals through one or more antennas (not shown).

Access point host 1304 communicates with each short-range wirelessmodule 1302 according to a host controller interface (HCI) 1312.Bluetooth specifies formats for messages and/or packets that cross HCIs1312 a and 1312 b. Examples of such standard messages include ashort-range wireless module 1302 requesting a link key from terminalhost 1304, and access point host 1304 providing a link key to therequesting short-range wireless module 1302.

Coverage area properties are determined by the manner in which modules1302 exchange RF signals. For instance, operational parameters, such astransmission power and antenna orientation, determine a coverage area'sshape, size, location, and orientation. To provide for dynamic coverageareas, access point host 1304 may store sets of such operationalparameters in memory 1306. Each of these parameter sets corresponds to apredetermined coverage area configuration. For each of these parametersets, access point host 1304 also stores a corresponding locationindicator.

To change a coverage area's characteristics, access point host 1304 maysend a command to a module 1302 across the corresponding HCI 1312. Thiscommand may include instructions, such as transmit power adjustment andantenna positioning directives. When a module 1302 receives such acommand, it makes appropriate transmission adjustments, and sends anacknowledgement message to access point host 1304.

Network interface 1308 provides connectivity to a data networkinfrastructure for enabling communication with at least one contentserver. For instance, in the context of FIGS. 9 and 12, networkinterface 1308 provides connectivity to gateways 112 and 1212,respectively. Alternatively, network interface 1308 may provide directconnectivity to data network 114.

As shown in FIG. 13, processor 1310 overlaps with short-rangecommunications modules 1302 a and 1302 b, access point host 1304, andnetwork interface 1308. This overlapping shows that functions performedby these elements may be handled by processor 1310. Processor 1310 andmemory 1306 may be implemented as described below with reference to FIG.15. For example, processor 1310 may be a commercially availablemicroprocessor.

Memory 1306 stores software components (e.g., instructions) thatprocessor 1310 executes to perform various operations. For instance,memory 1306 may store software components that enable the access pointto handle communications with content server 116 according to protocols,such as WAP and HTTP.

In addition, memory 1306 stores software instructions that allow accesspoint host 1304 to perform various features of the present invention.For example, these instructions provide for access point host 1304 toreceive a WCD-originated resource request through short-range wirelessmodule 1302 a or 1302 b. Once such a request is received, theseinstructions allow access point host 1304 to add information to theresource request, such as a location indicator. Then, the instructionsallow host 1304 to forward the resource requests, including the addedinformation to a content server, such as content server 116. Suchrequests are forwarded through network interface 1308.

These location indicators are based on the location of the coverage area904 corresponding to the short-range wireless module 1302 that receivedthe request. Thus, each short-range wireless module 1302 is assigned alocation indicator.

FIGS. 14A and 14B are elevation views involving a multiple coverage areascenario. In this scenario, two access points are located on differentlevels of a shopping mall. In particular, FIGS. 14A and 14B show a firstlevel and a second level that are separated by a floor 1401 b. An accesspoint 906 c having a coverage area 904 f is placed on the first level.Coverage area 904 f encompasses a shoe store 1402 and a restaurant 1404.Placed on the second level is an access point 906 d having coverageareas 904 g, 904 h, and 904 i. Floor 1401 b is constructed of amaterial, such as concrete. This prevents coverage areas 904 g-i fromoverlapping with coverage area 904 f.

In FIG. 14A, coverage areas 904 g-i cover a book store 1406, aninformational stand 1410, and a movie theater 1408, respectively. A useroperating WCD 1021 is within coverage area 904 g, while a user operatingWCD 102 m is within coverage area 904 i. These users each transmit arequest for the same resource. These requests are received by accesspoint 906 d. However, because of their different locations, these userseach receive different responses. As in the scenario of FIG. 8, theseresources may each be hypertext documents, such as WML or HTMLdocuments.

As shown in FIG. 14A, the user of WCD 102 l receives a “bookstore”resource, while the user of WCD 102 m receives a “movie theater”resource. This location-based content feature is provided through themultiple coverage area techniques described above.

FIG. 14B illustrates the dynamic coverage area feature of the presentinvention. FIG. 14B depicts a time during which book store 1406 isclosed. Because the bookstore is no longer open, access point 906 dchanges the properties of coverage area 904 h to better serve customersnear movie theater 1408. As shown in FIG. 14B, coverage area 904 g haschanged its size and orientation. As described above, these changes maybe performed through access point 906 d changing transmit power levelsand directional antenna orientations. In addition, access point 906 dchanges the location indicator associated with coverage area. Thislocation indicator change is reflected in databases, such as databases1002 and 1010.

As a result of these changes, when a content server receives a requestoriginating from within coverage area 904 g, it may return a resourcethat is different than the resource returned in FIG. 14A. For instance,FIG. 14B shows a user of WCD 102 n receiving a “movie theater” resourcein response to a request for “shoppingmall.com”. This resource wasreturned because the content server that delivered this resourceidentified a corresponding location indicator with movie theater 1408rather than book store 1406.

X. Computer System

As described above, various elements may be implemented with one or morecomputer systems. These elements include access points 106 and 906, hostcontrollers 110 and 910, gateways 112, 112′ and 1212, content server116, DHCP servers 502 and 1202, and connection manager servers 504 and1204. An example of a computer system 1501 is shown in FIG. 15.

Computer system 1501 represents any single or multi-processor computer.Single-threaded and multi-threaded computers can be used. Unified ordistributed memory systems can be used. Computer system 1501 includesone or more processors, such as processor 1504. One or more processors1504 can execute software implementing the processes described above.Each processor 1504 is connected to a communication infrastructure 1502(for example, a communications bus, cross-bar, or network). Varioussoftware embodiments are described in terms of this exemplary computersystem. After reading this description, it will become apparent to aperson skilled in the relevant art how to implement the invention usingother computer systems and/or computer architectures.

Computer system 1501 also includes a main memory 1507, which ispreferably random access memory (RAM). Computer system 1501 may alsoinclude a secondary memory 1508. Secondary memory 1508 may include, forexample, a hard disk drive 1510 and/or a removable storage drive 1512,representing a floppy disk drive, a magnetic tape drive, an optical diskdrive, etc. Removable storage drive 1512 reads from and/or writes to aremovable storage unit 1514 in a well known manner. Removable storageunit 1514 represents a floppy disk, magnetic tape, optical disk, etc.,which is read by and written to by removable storage drive 1512. As willbe appreciated, the removable storage unit 1514 includes a computerusable storage medium having stored therein computer software and/ordata.

In alternative embodiments, secondary memory 1508 may include othersimilar means for allowing computer programs or other instructions to beloaded into computer system 1501. Such means can include, for example, aremovable storage unit 1522 and an interface 1520. Examples can includea program cartridge and cartridge interface (such as that found in videogame devices), a removable memory chip (such as an EPROM, or PROM) andassociated socket, and other removable storage units 1522 and interfaces1520 which allow software and data to be transferred from the removablestorage unit 1522 to computer system 1501.

Computer system 1501 may also include a communications interface 1524.Communications interface 1524 allows software and data to be transferredbetween computer system 1501 and external devices via communicationspath 1527. Examples of communications interface 1527 include a modem, anetwork interface (such as Ethernet card), a communications port, etc.Software and data transferred via communications interface 1527 are inthe form of signals 1528 which can be electronic, electromagnetic,optical or other signals capable of being received by communicationsinterface 1524, via communications path 1527. Note that communicationsinterface 1524 provides a means by which computer system 1501 caninterface to a network such as the Internet.

The present invention can be implemented using software running (thatis, executing) in an environment similar to that described above withrespect to FIG. 15. In this document, the term “computer programproduct” is used to generally refer to removable storage units 1514 and1522, a hard disk installed in hard disk drive 1510, or a signalcarrying software over a communication path 1527 (wireless link orcable) to communication interface 1524. A computer useable medium caninclude magnetic media, optical media, or other recordable media, ormedia that transmits a carrier wave or other signal. These computerprogram products are means for providing software to computer system1501.

Computer programs (also called computer control logic) are stored inmain memory 1507 and/or secondary memory 1508. Computer programs canalso be received via communications interface 1524. Such computerprograms, when executed, enable the computer system 1501 to perform thefeatures of the present invention as discussed herein. In particular,the computer programs, when executed, enable the processor 1504 toperform the features of the present invention. Accordingly, suchcomputer programs represent controllers of the computer system 1501.

The present invention can be implemented as control logic in software,firmware, hardware or any combination thereof. In an embodiment wherethe invention is implemented using software, the software may be storedin a computer program product and loaded into computer system 1501 usingremovable storage drive 1512, hard drive 1510, or interface 1520.Alternatively, the computer program product may be downloaded tocomputer system 1501 over communications path 1527. The control logic(software), when executed by the one or more processors 1504, causes theprocessor(s) 1504 to perform the functions of the invention as describedherein.

In another embodiment, the invention is implemented primarily infirmware and/or hardware using, for example, hardware components such asapplication specific integrated circuits (ASICs). Implementation of ahardware state machine so as to perform the functions described hereinwill be apparent to persons skilled in the relevant art(s).

XI. Conclusion

While various embodiments of the present invention have been describedabove, it should be understood that they have been presented by way ofexample only, and not limitation. It will be apparent to persons skilledin the relevant art that various changes in form and detail can be madetherein without departing from the spirit and scope of the invention.Thus, the breadth and scope of the present invention should not belimited by any of the above-described exemplary embodiments, but shouldbe defined only in accordance with the following claims and theirequivalents.

1. A method of obtaining location-based information services,comprising: (a) receiving a resource request from an access point havinga plurality of coverage areas, the resource request originated by ashort-range wireless communications device (WCD) within one of theplurality of coverage areas; (b) adding to the resource request alocation indicator that identifies a location of the WCD, wherein thelocation indicator is based on said one coverage area; and (c)forwarding the resource request to a content server; said locationindicator being one of a plurality of location indicators, each of whichis capable of respectively identifying a location of the WCD within arespective one of said plurality of coverage areas of said access point.2. The method of claim 1, wherein the location indicator includeslocation coordinates.
 3. The method of claim 1, wherein said adding stepincludes inserting the location indicator into a Uniform ResourceLocator (URL).
 4. The method of claim 1, wherein said adding stepincludes inserting the location indicator into the resource request asone or more headers of the resource request.
 5. The method of claim 4,wherein said inserting step includes inserting the location indicatorinto the resource request as one or more extension headers.
 6. Themethod of claim 1, wherein the resource request is a hypertext transferprotocol (HTTP) request.
 7. The method of claim 1, wherein the locationindicator further indicates a vertical position of the WCD.
 8. Themethod of claim 1, wherein said step (b) comprises selectively addingthe location indicator to the resource request when the resource requestidentifies a suitable destination domain.
 9. The method of claim 1,wherein said step (b) comprises selectively adding the locationindicator to the resource request when the resource request isoriginated by one or more predetermined WCDs.
 10. The method of claim 1,further comprising adding user profile information to the resourcerequest.
 11. The method of claim 1, further comprising adding a deviceclass of the WCD to the resource request.
 12. The method of claim 1,further comprising adding an address of the WCD to the resource request.13. The method of claim 1, wherein the resource request is a wirelessapplication protocol (WAP) request.
 14. The method of claim 1, whereinthe WCD communicates with the access point across a Bluetooth wirelesscommunications link.
 15. The method of claim 1, wherein the locationindicator based on said one coverage area is predefined.
 16. The methodof claim 1, wherein the location indicator based on said one coveragearea dynamically changes.
 17. An apparatus for providing location-basedservices, the apparatus comprising: a location manager database thatstores location indicators for short-range wireless communicationsdevices (WCDs), wherein the location indicator for each WCD is based onone of a plurality of coverage areas associated with an access point,wherein the access point supports a wireless connection with the WCDthrough said one coverage area; a location appending unit configured toreceive resource requests originated by the WCDs, and for each request,to add the location indicator that corresponds to the requesting WCD;said location indicator being one of a plurality of location indicators,each of which is capable of respectively identifying a location of theWCD within a respective one of said plurality of coverage areas of saidaccess point.
 18. The apparatus of claim 17, wherein the locationmanager database stores the location indicators as location coordinates.19. The apparatus of claim 17, wherein the location appending unit isfurther configured to insert the location indicators into UniformResource Locators (URLs).
 20. The apparatus of claim 17, wherein thelocation appending unit is further configured to insert the locationindicators into the resource request as one or more headers of therequest.
 21. The apparatus of claim 20, wherein the location appendingunit is further configured to insert the location indicators into theresource request as one or more extension headers of the request. 22.The apparatus of claim 17, wherein the resource requests are hypertexttransfer protocol (HTTP) requests.
 23. The apparatus of claim 17,wherein the location indicators further indicate a vertical position ofthe WCDs.
 24. The apparatus of claim 17, wherein the location appendingunit is configured to selectively add location indicators to resourcerequests that identify suitable destination domains.
 25. The apparatusof claim 17, wherein the location appending unit is configured toselectively add location indicators to resource requests that areoriginated by one or more predetermined WCDs.
 26. The apparatus of claim17, wherein the location appending unit is further configured to adduser profile information to the resource requests.
 27. The apparatus ofclaim 17, wherein the location appending unit is further configured toadd WCD device classes to the resource requests.
 28. The apparatus ofclaim 17, wherein the location appending unit is further configured toadd WCD device addresses to the resource requests.
 29. The apparatus ofclaim 17, wherein the resource requests are wireless applicationprotocol (WAP) requests.
 30. The apparatus of claim 17, wherein at leastone of the location indicators is predefined.
 31. The apparatus of claim17, wherein at least one of the location indicators dynamically changes.32. A system for obtaining location-based information services,comprising: means for receiving a resource request from an access pointhaving a plurality of coverage areas, the resource request originated bya short-range wireless communications device (WCD) within one of theplurality of coverage areas; means for adding to the resource request alocation indicator that identifies a location of the WCD, wherein thelocation indicator is based on said one coverage area; and means forforwarding the resource request to a content server; said locationindicator being one of a plurality of location indicators, each of whichis capable of respectively identifying a location of the WCD within arespective one of said plurality of coverage areas of said access point.33. The system of claim 32, wherein the location indicator includeslocation coordinates.
 34. The system of claim 32, wherein said means foradding includes inserting the location indicator into a Uniform ResourceLocator (URL).
 35. The system of claim 32, wherein said means for addingincludes inserting the location indicator into the resource request asone or more headers of the resource request.
 36. The system of claim 35,wherein the one or more headers are extension headers.
 37. The system ofclaim 32, wherein the resource request is a hypertext transfer protocol(HTTP) request.
 38. The system of claim 32, wherein the locationindicator further indicates a vertical position of the WCD.
 39. Thesystem of claim 32, wherein said means for adding comprises means forselectively adding the location indicator to the resource request whenthe resource request identifies a suitable destination domain.
 40. Thesystem of claim 32, wherein said means for adding comprises means forselectively adding the location indicator to the resource request whenthe resource request is originated by one or more predetermined WCDs.41. The system of claim 32, further comprising means for adding userprofile information to the resource request.
 42. The system of claim 32,further comprising means for adding a device class of the WCD to theresource request.
 43. The system of claim 32, further comprising meansfor adding a device address of the WCD to the resource request.
 44. Thesystem of claim 32, wherein the resource request is a wirelessapplication protocol (WAP) request.
 45. The system of claim 32, whereinthe location indicator based on said one coverage area is predefined.46. The system of claim 32, wherein the location indicator based on saidone coverage area dynamically changes.
 47. A computer program productcomprising: a computer useable, tangible medium having computer programlogic recorded thereon for enabling a processor in a computer system toobtain location based services; program code in said computer programlogic, for enabling the processor to receive a resource request from anaccess point having a plurality of coverage areas, the resource requestoriginated by a short-range wireless communications device (WCD) withinone of the plurality of coverage areas; program code in said computerprogram logic, for enabling the processor to add to the resource requesta location indicator that identifies a location of the WCD, wherein thelocation indicator is based on said one coverage area; and program codein said computer program logic, for enabling the processor to forwardthe resource request to a content server; said location indicator beingone of a plurality of location indicators, each of which is capable ofrespectively identifying a location of the WCD within a respective oneof said plurality of coverage areas of said access point.
 48. Anapparatus for providing location-based services, comprising: a pluralityof short-range wireless access points, each configured to communicatewith one or more WCD devices through a corresponding coverage area; anetwork interface coupled to a data network infrastructure for enablingcommunication with at least one content server; a memory; a processorthat executes instructions stored in the memory for: receiving aresource request originated by a wireless communications device (WCD)through one of the short-range wireless access points; adding to theresource request a location indicator that identifies a location of theWCD, wherein the location indicator is based on the coverage areacorresponding to said one short-range wireless access point; andforwarding the resource request including the added location informationto a content server through the network interface; said locationindicator being one of a plurality of location indicators, each of whichis capable of respectively identifying a location of the WCD within arespective coverage area of one of said plurality of coverage areas ofsaid access point.
 49. The apparatus of claim 48, wherein the locationindicator is predefined.
 50. The apparatus of claim 48, wherein thelocation indicator dynamically changes.
 51. A method of obtaininglocation-based information services, comprising: (a) receiving aresource request originated by a short-range wireless communicationsdevice (WCD); (b) forwarding the resource request to a content server;(c) receiving from the content server an instruction for a locationindicator that identifies a location of the WCD; (d) determining thelocation indicator based on one of a plurality of coverage areasassociated with an access point, wherein the WCD communicates with theaccess point through said one coverage area, and (e) sending thelocation indicator to the content server; said location indicator beingone of a plurality of location indicators, each of which is capable ofrespectively identifying a location of the WCD within a respective oneof said plurality of coverage areas of said access point.